home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
deen095.zip
/
DEEN.DOC
next >
Wrap
Text File
|
1992-03-03
|
11KB
|
281 lines
D E E N 0.95 Echomail Message Encoder/Decoder
(C) 1992 Rubens Rahim
Legal: Use this program entirely at your own risk!
I will not be held responsible for ANYTHING that
happens through the use of this program. If you do
not agree to the above, DO NOT USE THIS!
Note:It is assumed that the reader possesses some knowledge on
DOS, Echomail, and BBS systems.
Introduction:
-------------
DEEN is a message decoder/encoder for echomail systems. It permits two
or more users to send private encoded echomail between each other over
public echomail networks. MAKE SURE YOU HAVE THE MODERATOR'S PERMISSION
BEFORE DOING THIS!!!!. This is especially useful for QWK based networks
where there is no real way to send private mail.
The encoded messages will stay within low-ASCII (32-127) and will not
affect any echomail processors. DEEN utilizes a KEY file system. Users
who want to send messages between each other must possess the same KEY
file. A utility to generate KEY files (KEYGEN.EXE) has been included.
More than 9.9 x 10^99 different KEY file combinations are possible.
A DIFFERENT KEYfile will be generated each time KEYGEN is run. Users
without the correct KEY file will NOT be able to decode messages,
even if they possess DEEN. Thus, DEEN can be used simultaneously among any
number of different users with no possibility of a security breach.
Instructions:
-------------
First, you should generate a KEY file. If someone else whom you want to
communicate with has already done so for you, obtain the KEY file from
him/her and skip this section.
To generate a KEY file, simply type
KEYGEN <keyfile>
where <keyfile> is a standard 8 character DOS filename. DO NOT USE
AN EXTENSION. .KEY will automatically be used. Give the keyfile
a name such that it will not be confused with other KEYfiles.
(e.g. if the KEY file is to be used for two people called Jack and Jill,
a name like JAK-JIL.KEY would be appropriate.)The KEY file will
be 7600 bytes long.
Once you've generated your KEY file, give everyone whom you want to
communicate privately with a copy of it. DO NOT GIVE IT TO ANYONE ELSE!!!!
Any number of KEY files can be generated, as long as they have
different filenames. You should generate as many KEY files as
you require.(Generally one for each individual or group of
individuals you want to communicate privately with.)
To send an encoded message:
---------------------------
This involves three processes: Typing the message, encoding the message,
and importing or inserting the encoded text into an echomail message.
First, type your message on a standard ASCII text editor. (e.g. Qedit,
DOS' EDIT, etc) MAKE SURE your text does not go to far to the right
(i.e. more than 80 columns wide) This will mess DEEN as well as your
BBS message editor up! Just to be sure, I would suggest keeping your
message within 70 columns. When you import your message, your BBS editor
must NOT have to word-wrap any line because it line is too long! Keep your
lines within the allowable width of your BBS editor. This is VERY, VERY
important! The message can be as many lines as you want, but it
MUST NOT contain any high-ASCII (Ansi graphics or anything above chr(127)).
This is to conform to FidoNET standards which do NOT allow high-ASCII!
Save the message to a disk file.
Next, type
DEEN <keyfile> encode <infile> <outfile>
<keyfile> is the name of the Keyfile you just created or were given.
Do NOT specify an extension! (e.g. JAK-JIL or JIM-DAVE)
'encode' can be abbreviated to 'e' if you feel like it....
<infile> is the ASCII text file you just typed. If you had an extension,
you must include that here too. Paths are fine. (e.g. LETTER1.TXT, etc...)
<outfile> is the encoded ASCII text file. It can be any legal 8+3 DOS
character filename. (e.g. LETTER1.DEC, OUT2, \BBS\MSG\MSG20.MDE, etc..)
DEEN will display the encoding process on the screen. It is fast!
Your encoded <outfile> will be created.
DEEN will NOT encode the message if any line is more than 80
columns long and/or any high-ASCII characters exist. A BEEP and an
error message will let you know if this happens. Fix it and simply
restart the process.
Logon to the BBS. Select 'Enter a message' or equivalent. Enter
the 'To:', 'From:' and 'Subject:' like any ordinary message.
Import or insert the encoded <outfile> into the BBS
message editor as if you were importing a regular ASCII text file into
a message. Save the message and make sure it is sent like any other
echomail message. Your BBS manual should have more information on this.
Example: Your original file <infile>
-----------------------------------------------------------------
Dear Helmut,
Thank you for your E-mail. I've just obtained this program called DEEN.
I think it is excellent. It now allows me to send private mail via
echomail at no extra cost. I just have to get you set up. Give me
your FidoNET address and I'll FSEND my KEY file to you.
Best regards.....Wolfgang
------------------------------------------------------------------
DEEN will create <outfile> that looks like this:
-------------------------------------------------------------------
qf<~I 6&SOs-
}4<0x#CGwb/PzF_il??I^:c?oAt,g<>s %isSi>ZL+VY@FM0z[_ n;s"!-+B#qk9P6'?B}~
5oj^OzIi)i!Y?FLNc$62- r*B{gNVr<s.TOgpN'%eBPo?<+{Q&Oc|+;cBU};FqCBf)
c!}(/UE&>ysSk#yHCRzrvjd,TAt,Xjoe@ySxO:'ZTBnY|F1Sx&(UxD}:DUzO=RCTj
yIg~I_E{r@Jk#dQ(D$E8vF[KB{>\89da]rc~-Y'z(F1aO|+8pl_(M|_
]f85Is69k|fG}v4'Y[W2lBc$:
-----------------------------------------------------------------------
As you can see, the encoded <outfile> consists only of regular keyboard
characters, maintaining the no-high-ASCII standard.
That's it! If you've done everything right, the other party should
receive and be able to decode your message.
To receive an encoded message:
------------------------------
Export the message to disk. (Get the message into a text file) Your BBS
manual will show you if you don't know how.
Make sure that the exported file has no extraneous text on the left or right.
Extra lines above and below the message are O.K. For example:
------------------------------------------------------------
To: Helmut Schmidt 26 Feb 1992
From: Wolfgang Mauer Msg 21/3992
Subj: Encoded Message.. Germany Chit-Chat Echo
qf<~I 6&SOs-
}4<0x#CGwb/PzF_il??I^:c?oAt,g<>s %isSi>ZL+VY@FM0z[_ n;s"!-+B#qk9P6'?B}~
5oj^OzIi)i!Y?FLNc$62- r*B{gNVr<s.TOgpN'%eBPo?<+{Q&Oc|+;cBU};FqCBf)
c!}(/UE&>ysSk#yHCRzrvjd,TAt,Xjoe@ySxO:'ZTBnY|F1Sx&(UxD}:DUzO=RCTj
yIg~I_E{r@Jk#dQ(D$E8vF[KB{>\89da]rc~-Y'z(F1aO|+8pl_(M|_
]f85Is69k|fG}v4'Y[W2lBc$:
---
* Origin: Ich liebe Deutschland, Baden-W (3:321/223)
-------------------------------------------------------------
The above is O.K. The actual encoded text is still intact.
(i.e. from left to right). The one below is NOT ok! because there are
line numbers on the left!
-----------------------------------------------------------
To: Helmut Schmidt 26 Feb 1992
From: Wolfgang Mauer Msg 21/3992
Subj: Encoded Message.. Germany Chit-Chat Echo
1:qf<~I 6&SOs-
2:
3:}4<0x#CGwb/PzF_il??I^:c?oAt,g<>s %isSi>ZL+VY@FM0z[_ n;s"!-+B#qk9P6'?B}~
4:5oj^OzIi)i!Y?FLNc$62- r*B{gNVr<s.TOgpN'%eBPo?<+{Q&Oc|+;cBU};FqCBf)
5:c!}(/UE&>ysSk#yHCRzrvjd,TAt,Xjoe@ySxO:'ZTBnY|F1Sx&(UxD}:DUzO=RCTj
6:yIg~I_E{r@Jk#dQ(D$E8vF[KB{>\89da]rc~-Y'z(F1aO|+8pl_(M|_
7:
8:]f85Is69k|fG}v4'Y[W2lBc$:
---
* Origin: Ich liebe Deutschland, Baden-W (3:321/223)
----------------------------------------------------------------
If you BBS software insists on putting text on the left or right
of the actual message text, the only way to make things work is to
go into a text editor and remove them yourself!
Once you have the message exported to a text file, exit to DOS and
type:
DEEN <keyfile> decode <textfile>
<keyfile> is the .KEY file. This MUST be the same one that was used
to encode the message.
'decode' can be abbreviated to 'd' if you feel like it.
<textfile> is the filename of the exported message text that you
obtained from the encoded echomail message (see above). DEEN will
output something like this:
DEEN 0.95 Message Encoder/Decoder (C)1992 Rubens Rahim
To: Helmut Schmidt 26 Feb 1992
From: Wolfgang Mauer Msg 21/3992
Subj: Encoded Message.. Germany Chit-Chat Echo
Dear Helmut,
Thank you for your E-mail. I've just obtained this program called DEEN.
I think it is excellent. It now allows me to send private mail via
echomail at no extra cost. I just have to get you set up. Give me
your FidoNET address and I'll FSEND my KEY file to you.
Best regards.....Wolfgang
---
* Origin: Ich liebe Deutschland, Baden-W (3:321/223)
As you can see, the message has been decoded. If you get an error
saying "Nothing found to decode", it probably means that spaces
or some other extraneous characters have been inserted on the left.
If you get the header ok (i.e. To: From:,etc) but a totally garbled
message, it probably means that your are using the wrong KEY.
Get the right KEYfile from the sender of the message. If you get the
message o.k. but garbled text on the right, it probably means that
spaces or other extraneous characters have been inserted on the right.
Final Note:
-----------
It is VERY important that you do not release any of your original
non-encoded message text files! Only the encoded version should be
sent via echomail. Releasing both the non-encoded and the encoded
version of any message will seriously undermine the security of
any other messages sent with the same KEYfile!!!! This should not
be a problem at all unless you give everyone you meet full access
to your hard disk! Obviously, you should not release your KEYfiles
publicly either! However, sending and receiving more than 1 message with
the same KEYfile is perfectly 100% safe! DEEN was designed for that.
Don't get paranoid! Keep your KEYfiles and original, non-encoded
messages safe, and you should be fine. The only thing that the general
public should be able to see is the encoded (garbled) message sent via
echomail. Nothing else. This should be quite obvious!
That's it! I've tested it, and it works for me. If it doesn't work for
you, I'd like to hear about it. I will try to help you. All comments,
criticisms, suggestions, pleas for help, bug reports (nah!...no way),
reports on grammatical errors in DOCs, etc can be sent to me via:
Snail Mail:
Rubens Rahim
4082 Virginia Cres.
North Vancouver, BC
Canada V7R 3Z1
Fidonet: Rubens Rahim 1:153/749 (can also be accessed via UUCP systems)
Fax: 1 (604) 980-7396
Voice: Not unless you know me personally!
BBS: 1 (604) 980-9078
I would especially like to hear from you if you have figured out a way
of decoding someone else's messages without possessing the key or any of
the original unencoded messages used with the key. I think it is
impossible. I may be wrong......
DEEN is public domain. You don't have to pay a cent for it. However,
if you're very rich and feel generous, you can send me any amount
you want through the above snail-mail address.
That's all.......Enjoy!